Received: from unknown (HELO geocities.com) (209.1.224.24) by pop.onelist.com with SMTP; 7 Sep 1998 10:16:01 -0000
Received: from geocities.com (ti28a61-0071.dialup.online.no [130.67.160.167]) by geocities.com (8.9.1/8.9.1) with ESMTP id DAA26957 for <amos-list@onelist.com>; Mon, 7 Sep 1998 03:18:13 -0700 (PDT)
Message-ID: <35F3B451.D912CBEE@geocities.com>
Date: Mon, 07 Sep 1998 12:24:17 +0200
From: TigerGutt <warewulf@geocities.com>
Organization: Organized ? ha ha ha
X-Mailer: Mozilla 4.06 [en] (Win98; I)
To: amos-list@onelist.com
References: <35EF3233.64E1@ozemail.com.au>
Mailing-List: list amos-list@onelist.com; contact http://www.onelist.com
Delivered-To: mailing list amos-list@onelist.com
Precedence: bulk
Reply-to: amos-list@onelist.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [amos-list] Re: LHA Trashing
Status: O
X-Status:
From: TigerGutt <warewulf@geocities.com>
I think this is due to the fact that netscape trashed the <cr> or
something. The same thing happends to mp3 files.
There is a tool on aminet for fixing this files i think.
Andy H wrote:
>
> From: Andy H <geosync@ozemail.com.au>
>
> Hi all,
>
> On the subject of LHA's being corrupted, I have found that some servers
> don`t recognize the LHA suffix and treat it as some sort of unspecific
> binary file (ergo goodbye LHA). The easiest way to stop this from
> happening is to archive as usual using LHA but rename it to #?.ZIP when
> sending it over the Internet. Most servers respect the archive
> structure of the IBM ZIP file and wont tamper with it. When the user
> recieves the "fake" ZIP file they can simply rename it and unpack with